- Replace all react-router-dom imports with @tanstack/react-router
- Update useNavigate() calls to use object syntax with `to` and `params`
- Replace useSearchParams with useSearch hook
- Replace matchPath with regex-based URL parsing
- Replace Navigate component with imperative navigate() calls
- Update useTimelineUrlState to use TanStack Router's search params API
- Replace navigate(-1) with window.history.back()
- Keep NavLink usage (TanStack Router supports it)
- Keep useOutletContext usage (TanStack Router supports it)

All navigation and routing functionality now uses TanStack Router APIs.

Add required arguments to useSearch, useParams, and useRouteContext calls:
- Generic hooks (useUrlState, useTimelineUrlState, useInviteValidation): use { strict: false }
- Page components bound to specific routes: use { from: routePath }
- Shared components (tab buttons, set cards): use { strict: false } with default values
- SetManagement/StageManagement: replace useRouteContext with useParams + query hook
- CSVImportPage: add validateSearch schema to route for tab param
- Remove unused FestivalEdition imports

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

- Navigation.tsx: Use router.history.back() instead of window.history.back()
  to integrate with TanStack Router's navigation system
- CSVImportPage: Simplify tab default to just use search.tab
- EditionLayout: Remove unnecessary EditionLayoutWrapper, use component directly
- SetManagement: Remove empty interface and unused comment
- searchSchemas: Move defaults and proper types to router-level Zod schemas
  - stages/genres: z.array(z.string()) instead of comma-separated strings
  - minRating: z.number() instead of z.string()
  - use24Hour/sortLocked: z.boolean() instead of z.string()
  - All fields use .catch() for defaults at the router level
- useUrlState: Simplified to thin wrapper over useSearch, removed manual
  parsing since router handles defaults and types
- useTimelineUrlState: Split updateState into individual update functions
  (updateView, updateDay, updateTime, updateStages) per review feedback.
  Exposed state properties at top level instead of nested state object.

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

- SetManagement: Use useSetsByEditionQuery instead of useSetsQuery to avoid client-side filtering
- StageManagement: Don't destruct queries, use full query objects
- FestivalSelection: Wire card click to handleFestivalClick for subdomain redirect logic
- useInviteValidation: Accept token as parameter instead of using useSearch internally
- __root: Use useSearch and pass invite token to useInviteValidation hook
- FestivalEdition: Type getCurrentSubTab return value as "sets" | "stages"
- CSVImportPage: Remove comment about not navigating with empty editionId
- .oxlintrc.json: Exclude routeTree.gen.ts from oxlint to allow 'as any' in generated code

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

Following the pattern established in useTimelineUrlState:
- Update useUrlState to accept page parameter ("sets" | "set-detail")
- Build route path internally using template literals with 'as const'
- Use route with both useSearch({ from: route }) and useNavigate({ from: route })
- Remove type assertions - TypeScript properly infers types with this pattern
- Update all callers to pass the page parameter

Updated components:
- ArtistsTab: uses "sets"
- SetDetails: uses "set-detail"
- ListFilters: uses "list" for timeline
- ListSchedule: uses "list" for timeline
- Timeline: uses "timeline" for timeline
- TimelineControls: uses "timeline" for timeline

This eliminates all usages of strict: false and provides proper type safety
without needing @ts-expect-error or type assertions.

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

1. FestivalSelection: Use Link with onClick handler for subdomain redirects
   - Restore Link component for better semantics and accessibility
   - Add onClick handler to intercept clicks on main domain
   - Prevents default and redirects to subdomain when needed
   - Allows normal Link navigation otherwise

2. __root.tsx: Remove strict: false from useSearch
   - Add validateSearch with Zod schema for root route
   - Define invite parameter as optional string
   - Use { from: "__root__" } for type-safe search access
   - Eliminates last usage of strict: false in codebase

All changes maintain existing behavior while improving type safety.

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

1. MobileTabButton: Remove unsupported render prop pattern
   - TanStack Router Link doesn't support {({ isActive }) => ...} pattern
   - Use useMatchRoute() to check if route is active
   - Conditionally style based on isActive state
   - Fixes runtime error with render props

2. FestivalEdition: Remove redundant redirect logic
   - beforeLoad in route already handles redirect to /stages
   - Remove duplicate useEffect that does the same redirect
   - Remove unused useEffect import

These changes fix the Copilot-identified issues while maintaining
existing behavior.

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

1. Edition Route - Implement data preloading in beforeLoad
   - Prefetch edition data using queryClient.ensureQueryData()
   - Makes data available to all child routes without blocking navigation
   - Follows TanStack Router preloading pattern for better UX
   - Reduces duplicate fetches across child components

2. FestivalEdition - Replace Tabs with Links
   - Convert Tabs component to semantic Link navigation
   - Better for accessibility and SEO
   - Proper browser back/forward behavior
   - Styled Links to look like tabs with active states

3. CSVImportPage - Fix navigation on festival change
   - Navigate to /admin/festivals/import when festival changes
   - Preserves tab in search params
   - Prevents stale URL params on page refresh
   - Added validateSearch schema to import route for tab param

All changes maintain existing behavior while following TanStack Router
best practices for preloading and navigation.

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX

The set detail route was missing the validateSearch schema, which
caused routing issues. The SetDetails component uses useUrlState()
which expects filterSortSearchSchema parameters (sort, stages, genres,
etc.) to be available.

Without the schema, the route couldn't properly match and the search
parameters weren't typed correctly.

Fixes: Set detail page now loads correctly at /sets/$setSlug

https://claude.ai/code/session_015h5PFMhsh3FgDeb2uEpKgX